-
Notifications
You must be signed in to change notification settings - Fork 239
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable addition OAuth 2.0 grant flows #83
Conversation
63b4d40
to
4a56bd5
Compare
var authorization = btoa(credentials.clientId + ':' + credentials.clientSecret); | ||
|
||
return { | ||
'Authorization': 'Bearer' + authorization |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we missing space after Bearer
?
Any thoughts about failed build? Just a noise? |
The broken build is because of this: In angular 1.2.16, they fixed some bugs, which the api-console relies on for rendering the (+) button at the last item of a repeatable named parameter: https://github.com/mulesoft/api-console/blob/master/app/views/repeatable.tmpl.html#L6 After that patch, the transcluded items do not share the same scope as the transcluder, and the the $last scope variable is no longer present in the transcluded scope. To fix this we would need a semi-major overhaul o named parameters. |
|
||
<div class="control-group" ng-if="credentials.grantType.type !== 'token'"> | ||
<label for="clientSecret"> | ||
<span class="required" ng-show="credentials.grantType.type !== 'owner'">*</span> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it be cleaner to do something like:
In CSS:
.required:after {
content: "*";
}
and then
<label for="clientSecret" ng-style:"{required: requiresSecret}">
and add to the controller:
$scope.requiresSecret = credentials.grantType.type !== 'token';
and remove the span?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably, I was just using what had already been implemented though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then let me rephrase:
I think we should do something like:
In CSS:
.required:after {
content: "*";
}
and then
<label for="clientSecret" ng-style:"{required: requiresSecret}">
and add to the controller:
$scope.requiresSecret = credentials.grantType.type !== 'token';
and remove the span.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, that change is now a part of this PR. It only changes one part of unrelated code.
05e7f37
to
4b59917
Compare
4b59917
to
a476695
Compare
LGTM |
@blakeembrey When you merge this one, can you also update the console version in api-designer and send me the SHAs, so I can update the tooling in our side? |
Don't forget to re-build console and designer. |
Enable addition OAuth 2.0 grant flows
No description provided.